home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group02b.txt
/
000040_icon-group-sender_Wed Sep 18 08:41:24 2002.msg
< prev
next >
Wrap
Internet Message Format
|
2003-01-02
|
1KB
Return-Path: <icon-group-sender>
Received: (from root@localhost)
by baskerville.CS.Arizona.EDU (8.11.1/8.11.1) id g8IFeQg14746
for icon-group-addresses; Wed, 18 Sep 2002 08:40:26 -0700 (MST)
Message-Id: <200209181540.g8IFeQg14746@baskerville.CS.Arizona.EDU>
Date: Wed, 18 Sep 2002 12:12:33 +0200
From: TrolletAtskynetDOTbe <complaint@nospam.org>
X-Accept-Language: en
X-Newsgroups: comp.lang.icon
Subject: Re: Icon Wish 2
X-Complaints-To: abuse@skynet.be
To: icon-group@cs.arizona.edu
Errors-To: icon-group-errors@cs.arizona.edu
Status: RO
Christopher Browne wrote:
> That's true; in theory, that ought to be a benefit of glomming onto
> "Perl Parrot," as the plan is to hook 'externs' to Perl through that
> level, and if that's the case, that buys "free hooks" for anyone else
> using Parrot for their own ends.
>
> While you can download, compile, and use Parrot today, there is
> certainly a lot of "vapor" to it...
Is there a place I can get a peek at it?
What is the 'amount of job' neccessary to change the Icon runtime to use
it?
Atle